-- card: 37683 from stack: in.0-2
-- bmap block id: 2414
-- flags: 0000
-- background id: 36952
-- name: Show CommonQs
----- HyperTalk script -----
-- This handler stores the name of the last card.
on goBack
  go cd "Common User Que" of stack "Intro to HyperCard 2.0"
end goBack


-- part 4 (field)
-- low flags: 01
-- high flags: 0000
-- rect: left=64 top=70 right=103 bottom=400
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 174
-- text size: 12
-- style flags: 16640
-- line height: 14
-- part name: TitleFld


-- part 5 (field)
-- low flags: 01
-- high flags: 0000
-- rect: left=64 top=102 right=290 bottom=404
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 174
-- text size: 14
-- style flags: 0
-- line height: 15
-- part name: TextDisplay


-- part 8 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=44 top=48 right=294 bottom=421
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: wind


-- part 2 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=51 top=50 right=65 bottom=71
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: closebox
----- HyperTalk script -----
-- This handler sets the cursor to simulate a real closeBox.
on mouseEnter
  set the cursor to "arrow"
end mouseEnter

-- This handler sets the cursor to simulate a real closeBox.
on mouseWithIn
  repeat until the mouse is down or the mouseLoc is not within the rect of me
    set the cursor to "arrow"
  end repeat
  if the mouse is down then
    send mouseUp to me
  end if
end mouseWithIn

-- This handler simulates clicking in a closeBox.
on mouseUp
  set the icon of me to "closeBoxIcon"
  wait 15
  set the icon of me to 0
  goBack
end mouseUp


-- part 6 (field)
-- low flags: 81
-- high flags: 0007
-- rect: left=0 top=0 right=309 bottom=475
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 3
-- text size: 9
-- style flags: 0
-- line height: 12
-- part name: Text


-- part contents for card part 6
----- text -----
[0] 
[1] Yes, HyperCard will work on 1MB systems, but some features, like multiple windows, are memory dependent, and so may be limited by the user’s system configuration. Other features, like scrolling the window to see large cards, will degrade when memory is short. Users who add more internal memory to their systems will have better access to these features of HyperCard 2.0.
[2] Color bitmaps, because of their size, have large performance and storage requirements. Color PICT files, while small on disk, have other performance penalties. Including color would cause HyperCard’s performance to be unsatisfactory for most of our users, who have 8 MHz, black-and-white CPUs. Apple will continue to encourage third-parties to add color-functionality to HyperCard for customers who desire it, and will work to have HyperCard support high-quality color extensions.
[3] Future releases of HyperCard will support System 7.0. Some features of System 7.0 are transparent to HyperCard (like resolution-independent graphics & Macintosh Outline Fonts), and require no additions to HyperCard. Other features (like the Inter-Application Communications Architecture (IACA))  will require additional development.
[4] Absolutely not. HyperCard is a key piece of the Apple platform. It offers functionality that our users expect, and Apple will continue to offer and enhance that functionality.
[5] Parts of HyperCard will become part of the Operating System so that all applications, not just HyperCard stacks, can take advantage of HyperCard’s power. For instance, Apple plans to add HyperCard’s super-fast bit-map algorithm to the Macintosh Toolbox. By moving such parts of HyperCard into the Operating System, HyperCard’s functionality is not only spread around, but more room is made for additional features. HyperCard will function as shared-code library, offering resources & routines for stacks to use.
[6] Apple does not discuss projects that may or may not be under development. Keep in mind, however, that performance, extensibility, and simplicity are major objectives for HyperCard development. Adding object graphics to HyperCard would also add size and complexity to the software; this may work against Apple’s goal of keeping HyperCard fast, simple, and well-integrated for users. Future extensibility in HyperCard may make it possible for third-party developers to create, add, and market such functionality.
[7] Apple encourages third-party development to enhance our platform. Developers have always been strategic partners with Apple in creating the personal computer marketplace. The other Hypertext and multimedia applications available for the Macintosh computer extend HyperCard’s functionality in a number of ways. For users who need capabilities other than HyperCard can offer, the other applications are good options.
[8] 


-- part contents for card part 4
----- text -----
What does Apple think of other Hypertext applications for the Macintosh computer?

-- part contents for card part 5
----- text -----
Apple encourages third-party development to enhance our platform. Developers have always been strategic partners with Apple in creating the personal computer marketplace. The other Hypertext and multimedia applications available for the Macintosh computer extend HyperCard’s functionality in a number of ways. For users who need capabilities other than HyperCard can offer, the other applications are good options.